Skip to content

feat(react): Mark errors captured from ErrorBoundary as unhandled #8914

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 4, 2023

Conversation

Lms24
Copy link
Member

@Lms24 Lms24 commented Aug 30, 2023

This PR is part of a series of PRs adjusting the exception mechanism's handled value.

For more details see #8890

Changed Instrumentation

This PR addresses the mechanisms set in the React package, more concretely in our ErrorBoundary.

ref #6073

@Lms24 Lms24 merged commit 3d8b444 into develop Sep 4, 2023
@Lms24 Lms24 deleted the lms/fix-handled-unhandled-react branch September 4, 2023 11:57
Lms24 added a commit that referenced this pull request Mar 8, 2024
#10989)

Previously, we made a change to always mark such errors as unhandled
(#8914). However, as pointed out and discussed in #10985, this isn't
always the best default value. I propose we set handled/unhandled
depending on the presence of the `fallback` component. If users specify
a fallback, I think it's safe to mark the error handled, given that
users show something else instead of the errored component.
Lms24 added a commit that referenced this pull request Mar 12, 2024
#10989)

Previously, we made a change to always mark such errors as unhandled
(#8914). However, as pointed out and discussed in #10985, this isn't
always the best default value. I propose we set handled/unhandled
depending on the presence of the `fallback` component. If users specify
a fallback, I think it's safe to mark the error handled, given that
users show something else instead of the errored component.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants